ARM (Control Plane) API Specification Update Pull Request

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

• New resource provider.
• New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
• Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
• Update existing version to fix OpenAPI spec quality issues in S360.
• Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
• Other, please clarify:
  • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

• I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• I have reviewed following Resource Provider guidelines, including
  ARM resource provider contract and
  REST guidelines (estimated time: 4 hours).
  I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
• A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

Additional information

This PR fixes the failing TypeSpec Validation CI job for the ContainerInstance 2026-07-01 stable API version.

Root cause: The TypeSpec source example file examples/2026-07-01/ContainerGroupsCreateOrUpdateManagedIdentityAzureFileshare.json used the property name userManagedIdentityClientId, while the TypeSpec model (models.tsp) and the generated swagger definition (containerInstance.json) define the property as userAssignedIdentityClientId. When tsp compile ran in CI, it copied the source example value (userManagedIdentityClientId) into the generated output file, producing a diff against the committed file and triggering the "files have been changed after tsp compile" validation failure.

Fix: Updated the source example file to use userAssignedIdentityClientId (matching the TypeSpec model property name and the swagger definition), so tsp compile now generates output consistent with the committed file — no diff, no failure.

Files changed:

• specification/containerinstance/resource-manager/Microsoft.ContainerInstance/ContainerInstance/examples/2026-07-01/ContainerGroupsCreateOrUpdateManagedIdentityAzureFileshare.json — replaced userManagedIdentityClientId with userAssignedIdentityClientId (3 occurrences)

Getting help

• First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.
• For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.